|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 43
|
|
Title:
|
Virtual NID (vNID) Functionality for E-Access Services
This document specifies the functionality offered by an Access Provider (AP) that, when
combined with an Ethernet-Access (E-Access) Service, allows a Service Provider (SP) to
monitor and configure selected objects associated with a given UNI and one or more OVC End
Points at that UNI in the AP’s network. The effect is that the AP provides functionality similar to
what would otherwise require the SP to place a Network Interface Device (NID) at the
customer’s location. Hence, the AP is said to be providing “virtual NID (vNID)” functionality to
the E-Access Service that the SP has purchased. This is accomplished via the SP communicating
over a Remote Management Interface (RMI) Connection to the AP, using an RMI Protocol.
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2015
|
|
3.
|
Justification for the specific reference:
|
|
|
The virtual NID E-access service [MEF 43] address the case where the SP does not have to deploy an additional network interface device (NID) to form a basis for this Recommendation
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
No known issues.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Commonly referenced all over the world for metro Ethernet services.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Commonly referenced all over the world for metro Ethernet services.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] IEEE Std 802.1Q-2011, "Virtual Bridged Local Area Networks", 2011/
[2] IEEE Std 802.3-2012, IEEE Standard for Ethernet, 28 December 2012./
[3] IEEE Std 802.3.1-2011, IEEE Standard for Management Information Base (MIB)/
Module Definitions for Ethernet, 5 July 2011/
[4] IETF RFC 768, User Datagram Protocol, August 1980./
[5] IETF RFC 791, Internet Protocol, September 1981./
[6] IETF RFC 792, Internet Control Message Protocol, September 1981/
[7] IETF RFC 793, Transmission Control Protocol, September 1981/
[8] IETF RFC 826, Ethernet Address Resolution Protocol: Or Converting Network/
Protocol Addresses to 48-bit Ethernet Address for Transmission on Ethernet/
Hardware, November 1982/
[9] IETF RFC 959, File Transfer Protocol, October 1985/
Virtual NID (vNID) Functionality for E-Access Services/
[10] IETF RFC 1907, Management Information Base for Version 2 of the Simple/
Network Management Protocol (SNMPv2), January 1996/
[11] IETF RFC 2119, Bradner, S., Key words for use in RFCs to Indicate Requirement/
Levels, March 1997. (Normative)/
[12] IETF RFC 2570, Introduction to Version 3 of the Internet-standard Network/
Management Framework, April 1999/
[13] IETF RFC 2576, Coexistence between Version 1, Version 2, and Version 3 of the/
Internet-standard Network Management Framework, March 2000/
[14] IETF RFC 2578, Structure of Management Information Version 2 (SMIv2), April/
1999/
[15] IETF RFC 2579, Textual Conventions for SMIv2, April 1999/
[16] IETF RFC 2580, Conformance Statements for SMIv2, April 1999/
[17] IETF RFC 3339, Date and Time on the Internet: Timestamps, July 2002/
[18] IETF RFC 3411, An Architecture for Describing Simple Network Management/
Protocol (SNMP) Management Frameworks, December 2002/
[19] IETF RFC 3412, Message Processing and Dispatching for the Simple Network/
Management Protocol (SNMP), December 2002/
[20] IETF RFC 3413, Simple Network Management Protocol (SNMP) Applications,/
December 2002/
[21] IETF RFC 3414, User-based Security Model (USM) for version 3 of the Simple/
Network Management Protocol (SNMPv3), December 2002/
[22] IETF RFC 3415, View-based Access Control Model (VACM) for the Simple/
Network Management Protocol (SNMP), December 2002/
[23] IETF RFC 3416, Version 2 of the Protocol Operations for the Simple Network/
Management Protocol (SNMP), December 2002/
[24] IETF RFC 3417, Transport Mappings for the Simple Network Management/
Protocol (SNMP), December 2002/
[25] IETF RFC 3418, Management Information Base (MIB) for the Simple Network/
Management Protocol (SNMP), December 2002/
[26] IETF RFC 4250, The Secure Shell (SSH) Protocol Assigned Numbers, January/
2006/
[27] IETF RFC 4251, The Secure Shell (SSH) Protocol Architecture, January 2006/
[28] IETF RFC 4252, The Secure Shell (SSH) Authentication Protocol, January 2006/
[29] IETF RFC 4253, The Secure Shell (SSH) Transport Layer Protocol, January 2006/
[30] IETF RFC 4254, The Secure Shell (SSH) Connection Protocol, January 2006/
Virtual NID (vNID) Functionality for E-Access Services/
[31] IETF RFC 4255, Using DNS to Securely Publish Secure Shell (SSH) Key/
Fingerprints, January 2006/
[32] IETF RFC 4256, Generic Message Exchange Authentication for the Secure Shell/
Protocol (SSH), January 2006/
[33] IETF RFC 4291, R. Hinden, S. Deering, IP Version 6 Addressing Architecture,/
February 2006/
[34] IETF RFC 4443, A. Contra, et. al., Internet Control Message Protocol (ICMPv6)/
for the Internet Protocol Version 6 (IPv6) Specification, March, 2006./
[35] IETF RFC 4742, T. Wasserman and T. Goddard, Using the NETCONF/
Configuration Protocol over Secure Shell (SSH), December 2006./
[36] IETF RFC 4861, T. Narten, et. al., Neighbor Discovery for IP version 6 (IPv6),/
September 2007./
[37] IETF RFC 4862, IPv6 Stateless Address Autoconfiguration, September 2007/
[38] IETF RFC 4878, M. Squire, Definitions and Managed Objects for Operations,/
Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces,/
June 2007/
[39] IETF RFC 5277, NETCONF Event Notifications, July 2008/
[40] IETF RFC 6020, M. Bjorklund, Ed., YANG - A data modeling language for the/
Network Configuration Protocol (NETCONF), October 2010./
[41] IETF RFC 6241, R. Enns, M. Bjorklund, J. Schoenwaelder, A. Bierman, Network/
Configuration Protocol (NETCONF), June 2011./
[42] IETF STD 62, Simple Network Management Protocol Version 3 (SNMPv3), D./
Harrington, R. Presuhn, B. Wijnen, J. Case, D. Levi, P. Meyer, B. Stewart, U./
Blumenthal, K. McCloghrie, December 2002/
(Note, this includes the package of RFCs 3411-3418)/
[43] ITU-T Recommendation G.8013/Y.1731, Edition 3 (07/2001), "OAM functions/
and mechanisms for Ethernet based Networks"./
[44] ITU-T Recommendation G.8021/Y.1341 (05/2012), Characteristics of Ethernet/
Transport Network Equipment Functional Blocks/
[45] ITU-T Recommendation M.3100 (04/2005), Generic network information model./
[46] ITU-T Recommendation Q.840.1 (2007), Requirements and Analysis for NMSEMS/
Management Interface of Ethernet over Transport and Metro Ethernet/
Network./
[47] MEF Technical Specification MEF 4, "Metro Ethernet Network Architecture/
Framework - Part 1: Generic Framework", May 2004./
[48] MEF Technical Specification MEF 6.1, "Ethernet Services Definitions - Phase 2",/
April 2008./
Virtual NID (vNID) Functionality for E-Access Services/
[49] MEF Technical Specification MEF 6.1.1, " Layer 2 Control Protocol Handling/
Amendment to MEF 6.1”, January 2012./
[50] MEF Technical Specification MEF 7.2, "Carrier Ethernet Management/
Information Model", April 2013./
[51] MEF Technical Specification MEF 10.2, "Ethernet Services Attributes Phase 2",/
October 2009./
[52] MEF Technical Specification MEF 10.2.1, “Performance Attributes Amendment/
to MEF 10.2”, January 2011./
[53] MEF Technical Specification MEF 12.1, “Carrier Ethernet Network Architecture/
Framework, Part 2: Ethernet Services Layer – Base Elements”, April 2010./
[54] MEF Technical Specification MEF 15, "Requirements for Management of Metro/
Ethernet Phase 1 Network Elements", November 2005./
[55] MEF Technical Specification MEF 16, "Ethernet Local Management Interface (ELMI),/
January 2006./
[56] MEF Technical Specification MEF 17, "Service OAM Requirements &/
Framework - Phase 1", April 2007./
[57] MEF Technical Specification MEF 20, "User Network Interface (UNI) Type 2/
Implementation Agreement", July 2008./
[58] MEF Technical Specification MEF 23.1, “Carrier Ethernet Class of Service –/
Phase 2”, January 2012./
[59] MEF Technical Specification MEF 26.1, "External Network Network Interface/
(ENNI) - Phase 2", January 2012./
[60] MEF Technical Specification MEF 28, "External Network Network Interface/
(ENNI) Support for UNI Tunnel Access and Virtual UNI", October 2010./
[61] MEF Technical Specification MEF 30.1, "Service OAM Fault Management/
Implementation Agreement: Phase 2", April 2013./
[62] MEF Technical Specification MEF 31, “Service OAM Fault Management/
Definition of Managed Objects”, January 2011./
[63] MEF Technical Specification MEF 31.0.1, “Amendment to Service OAM SNMP/
MIB for Fault Management”, January 2012./
[64] MEF Technical Specification MEF 33, "Ethernet Access Services Definition ",/
January 2012./
[65] MEF Technical Specification MEF 35, “Service OAM Performance Monitoring/
Implementation Agreement”, April 2012./
[66] MEF Technical Specification MEF 36, “Service OAM SNMP MIB for/
Performance Monitoring”, January 2012./
Virtual NID (vNID) Functionality for E-Access Services/
[67] MEF Technical Specification MEF 39, "Service OAM Performance Monitoring/
YANG Module”, April 2012./
[68] MEF Technical Specification MEF 40, "UNI and EVC Definition of Managed/
Objects", April 2013./
[69] MEF Technical Specification MEF 42, "ENNI and OVC Definition of Managed/
Objects", October 2013./
[70] MEF Technical Specification MEF 44, “vNID Definition of Managed Objects",/
April 2014.
|
|
9.
|
Qualification of
MEF:
|
|
|
The MEF was recognized under the provisions of ITU-T Recommendation A.5 on 24 September 2002. Qualifying information is on file with TSB.
9.5 The IPR policy of the MEF may be found in Article 10 of the MEF Bylaws which are available on the MEF public WEB site metroethernetforum.org.
9.6 All MEF Technical Specifications, Implementation Agreements, and Test Specifications are approved by an electronic letter ballot of all MEF members. For a MEF document to pass an electronic letter ballot at least a quorum of members (defined by the MEF bylaws as 1/3 of the MEF membership) must vote Yes or No. In addition, of the Yes plus No votes at least 75% of the votes must be Yes.
9.7 All published MEF documents are available for download free of charge in PDF or WORD format from the MEF public WEB site www.metroethernetforum.org .
9.8 Each revision of a given MEF document has a different MEF number.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
